SherbyNet - /page/wikibook/entry.mu

Micron Document

<!DOCTYPE html>

<title>Transaction processing</title>

</head>

<span id="openzim-page-title" class="mw-page-title-main"><span class="mw-page-title-main">Transaction processing</span></span>

</h1>

</header>

/* start https://en.wikipedia.org/ */

.mw-parser-output .hatnote{font-style:italic}.mw-parser-output div.hatnote{padding-left:1.6em;margin-bottom:0.5em}.mw-parser-output .hatnote i{font-style:normal}.mw-parser-output .hatnote+link+.hatnote{margin-top:-0.5em}@media print{body.ns-0 .mw-parser-output .hatnote{display:none!important}}

/* end https://en.wikipedia.org/ */

</style><div role="note" class="hatnote navigation-not-searchable">For other uses, see <a href="Transaction_(disambiguation)" class="mw-redirect mw-disambig" title="Transaction (disambiguation)">Transaction (disambiguation)</a>.</div>

<div role="note" class="hatnote navigation-not-searchable">This article is about the principles of transaction processing. For specific implementations, see <a href="Transaction_processing_system" title="Transaction processing system">Transaction processing system</a>.</div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .ambox{border:1px solid #a2a9b1;border-left:10px solid #36c;background-color:#fbfbfb;box-sizing:border-box}.mw-parser-output .ambox+link+.ambox,.mw-parser-output .ambox+link+style+.ambox,.mw-parser-output .ambox+link+link+.ambox,.mw-parser-output .ambox+.mw-empty-elt+link+.ambox,.mw-parser-output .ambox+.mw-empty-elt+link+style+.ambox,.mw-parser-output .ambox+.mw-empty-elt+link+link+.ambox{margin-top:-1px}html body.mediawiki .mw-parser-output .ambox.mbox-small-left{margin:4px 1em 4px 0;overflow:hidden;width:238px;border-collapse:collapse;font-size:88%;line-height:1.25em}.mw-parser-output .ambox-speedy{border-left:10px solid #b32424;background-color:#fee7e6}.mw-parser-output .ambox-delete{border-left:10px solid #b32424}.mw-parser-output .ambox-content{border-left:10px solid #f28500}.mw-parser-output .ambox-style{border-left:10px solid #fc3}.mw-parser-output .ambox-move{border-left:10px solid #9932cc}.mw-parser-output .ambox-protection{border-left:10px solid #a2a9b1}.mw-parser-output .ambox .mbox-text{border:none;padding:0.25em 0.5em;width:100%}.mw-parser-output .ambox .mbox-image{border:none;padding:2px 0 2px 0.5em;text-align:center}.mw-parser-output .ambox .mbox-imageright{border:none;padding:2px 0.5em 2px 0;text-align:center}.mw-parser-output .ambox .mbox-empty-cell{border:none;padding:0;width:1px}.mw-parser-output .ambox .mbox-image-div{width:52px}@media(min-width:720px){.mw-parser-output .ambox{margin:0 10%}}@media print{body.ns-0 .mw-parser-output .ambox{display:none!important}}

/* end https://en.wikipedia.org/ */

</style>

<p>In <a href="Computer_science" title="Computer science">computer science</a>, <b>transaction processing</b> is information processing <sup id="cite_ref-Gray_1-0" class="reference"><a href="#cite_note-Gray-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup> that is divided into individual, indivisible operations called <i>transactions</i>. Each transaction must succeed or <a href="Failure" title="Failure">fail</a> as a complete unit; it can never be only partially complete.

</p><p>For example, when you purchase a book from an online bookstore, you exchange money (in the form of <a href="Credit" title="Credit">credit</a>) for a book. If your credit is good, a series of related operations ensures that you get the book and the bookstore gets your money. However, if a single operation in the series fails during the exchange, the entire exchange fails. You do not get the book and the bookstore does not get your money. The technology responsible for making the exchange balanced and predictable is called <i>transaction processing</i>. Transactions ensure that data-oriented resources are not permanently updated unless all operations within the transactional unit complete successfully. By combining a set of related operations into a unit that either completely succeeds or completely fails, one can simplify error recovery and make one's application more reliable.

</p><p>Transaction processing systems consist of computer hardware and software hosting a transaction-oriented application that performs the routine transactions necessary to conduct business. Examples include systems that manage sales order entry, airline reservations, payroll, employee records, manufacturing, and shipping.

</p><p>Since most, though not necessarily all, transaction processing today is interactive, the term is often treated as synonymous with <i><a href="Online_transaction_processing" title="Online transaction processing">online transaction processing</a></i>.

</p>

<div class="mw-heading mw-heading2"><h2 id="Description">Description</h2></div>

<p>Transaction processing is designed to maintain a system's Integrity (typically a <a href="Database" title="Database">database</a> or some modern <a href="Filesystem" class="mw-redirect" title="Filesystem">filesystems</a>) in a known, consistent state, by ensuring that interdependent operations on the system are either all completed successfully or all canceled successfully.

</p><p>For example, consider a typical banking transaction that involves moving $700 from a customer's savings account to a customer's checking account. This transaction involves at least two separate operations in computer terms: debiting the savings account by $700, and crediting the checking account by $700. If one operation succeeds but the other does not, the books of the bank will not balance at the end of the day. There must, therefore, be a way to ensure that either both operations succeed or both fail so that there is never any inconsistency in the bank's database as a whole.

</p><p>Transaction processing links multiple individual operations in a single, indivisible transaction, and ensures that either all operations in a transaction are completed without error, or none of them are. If some of the operations are completed but errors occur when the others are attempted, the transaction-processing system "rolls back" <i>all</i> of the operations of the transaction (including the successful ones), thereby erasing all traces of the transaction and restoring the system to the consistent, known state that it was in before processing of the transaction began. If all operations of a transaction are completed successfully, the transaction is <a href="Commit_(data_management)" title="Commit (data management)">committed</a> by the system, and all changes to the database are made permanent; the transaction cannot be rolled back once this is done.

</p><p>Transaction processing guards against hardware and software errors that might leave a transaction partially completed. If the computer system crashes in the middle of a transaction, the transaction processing system guarantees that all operations in any uncommitted transactions are cancelled.

</p><p>Generally, transactions are issued concurrently. If they overlap (i.e. need to touch the same portion of the database), this can create conflicts. For example, if the customer mentioned in the example above has $150 in his savings account and attempts to transfer $100 to a different person while at the same time moving $100 to the checking account, only one of them can succeed. However, forcing transactions to be processed sequentially is inefficient. Therefore, concurrent implementations of transaction processing is programmed to guarantee that the end result reflects a conflict-free outcome, the same as could be reached if executing the transactions sequentially in any order (a property called <a href="Serializability" class="mw-redirect" title="Serializability">serializability</a>). In our example, this means that no matter which transaction was issued first, either the transfer to a different person or the move to the checking account succeeds, while the other one fails.

</p>

<div class="mw-heading mw-heading2"><h2 id="Methodology">Methodology</h2></div>

<p>The basic principles of all transaction-processing systems are the same. However, the terminology may vary from one transaction-processing system to another, and the terms used below are not necessarily universal.

</p>

<div class="mw-heading mw-heading3"><h3 id="Rollback">Rollback</h3></div>

<div role="note" class="hatnote navigation-not-searchable">Main article: <a href="Rollback_(data_management)" title="Rollback (data management)">Rollback (data management)</a></div>

<p>Transaction-processing systems ensure database integrity by recording intermediate states of the database as it is modified, then using these records to restore the database to a known state if a transaction cannot be committed. For example, copies of information on the database <i>prior</i> to its modification by a transaction are set aside by the system before the transaction can make any modifications (this is sometimes called a <i>before image</i>). If any part of the transaction fails before it is committed, these copies are used to restore the database to the state it was in before the transaction began.

</p>

<div class="mw-heading mw-heading3"><h3 id="Rollforward">Rollforward</h3></div>

<p>It is also possible to keep a separate <a href="Journal_(computing)" class="mw-redirect" title="Journal (computing)">journal</a> of all modifications to a database management system. (sometimes called <i>after images</i>). This is not required for rollback of failed transactions but it is useful for updating the database management system in the event of a database failure, so some transaction-processing systems provide it. If the database management system fails entirely, it must be restored from the most recent back-up. The back-up will not reflect transactions committed since the back-up was made. However, once the database management system is restored, the journal of after images can be applied to the database (<i>rollforward</i>) to bring the database management system up to date. Any transactions in progress at the time of the failure can then be rolled back. The result is a database in a consistent, known state that includes the results of all transactions committed up to the moment of failure.

</p>

<div class="mw-heading mw-heading3"><h3 id="Deadlocks">Deadlocks</h3></div>

<div role="note" class="hatnote navigation-not-searchable">Main article: <a href="Deadlock_(computer_science)" title="Deadlock (computer science)">Deadlock (computer science)</a></div>

<p>In some cases, two transactions may, in the course of their processing, attempt to access the same portion of a database at the same time, in a way that prevents them from proceeding. For example, transaction A may access portion X of the database, and transaction B may access portion Y of the database. If at that point, transaction A then tries to access portion Y of the database while transaction B tries to access portion X, a <i>deadlock</i> occurs, and neither transaction can move forward. Transaction-processing systems are designed to detect these deadlocks when they occur. Typically both transactions will be cancelled and rolled back, and then they will be started again in a different order, automatically, so that the deadlock does not occur again. Or sometimes, just one of the deadlocked transactions will be cancelled, rolled back, and automatically restarted after a short delay.

</p><p>Deadlocks can also occur among three or more transactions. The more transactions involved, the more difficult they are to detect, to the point that transaction processing systems find there is a practical limit to the deadlocks they can detect.

</p>

<div class="mw-heading mw-heading3"><h3 id="Compensating_transaction">Compensating transaction</h3></div>

<p>In systems where commit and rollback mechanisms are not available or undesirable, a <a href="Compensating_transaction" title="Compensating transaction">compensating transaction</a> is often used to undo failed transactions and restore the system to a previous state.

</p>

<div class="mw-heading mw-heading2"><h2 id="ACID_criteria">ACID criteria</h2></div>

<div role="note" class="hatnote navigation-not-searchable">Main article: <a href="ACID" title="ACID">ACID</a></div>

<p><a href="Jim_Gray_(computer_scientist)" title="Jim Gray (computer scientist)">Jim Gray</a> defined properties of a reliable transaction system in the late 1970s under the acronym <i>ACID</i>—atomicity, consistency, isolation, and durability.<sup id="cite_ref-Gray_1-1" class="reference"><a href="#cite_note-Gray-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup>

</p>

<div class="mw-heading mw-heading3"><h3 id="Atomicity">Atomicity</h3></div>

<div role="note" class="hatnote navigation-not-searchable">Main article: <a href="Atomicity_(database_systems)" title="Atomicity (database systems)">Atomicity (database systems)</a></div>

<p>A transaction's changes to the state are atomic: either all happen or none happen. These changes include database changes, messages, and actions on transducers.

</p>

<div class="mw-heading mw-heading3"><h3 id="Consistency">Consistency</h3></div>

<p><a href="Consistency_(database_systems)#Consistency" title="Consistency (database systems)">Consistency</a>: A transaction is a correct transformation of the state. The actions taken as a group do not violate any of the integrity constraints associated with the state.

</p>

<div class="mw-heading mw-heading3"><h3 id="Isolation">Isolation</h3></div>

<p>Even though transactions execute concurrently, it appears to each transaction T, that others executed either before T or after T, but not both.

</p>

<div class="mw-heading mw-heading3"><h3 id="Durability">Durability</h3></div>

<p>Once a transaction completes successfully (commits), its changes to the database survive failures and retain its changes.

</p>

<div class="mw-heading mw-heading2"><h2 id="Implementations">Implementations</h2></div>

<div role="note" class="hatnote navigation-not-searchable">Main article: <a href="Transaction_processing_system" title="Transaction processing system">Transaction processing system</a></div>

<p>Standard transaction-processing <a href="Software" title="Software">software</a>, such as <a href="IBM" title="IBM">IBM</a>'s <a href="Information_Management_System" class="mw-redirect" title="Information Management System">Information Management System</a>, was first developed in the 1960s, and was often closely coupled to particular <a href="Database_management_system" class="mw-redirect" title="Database management system">database management systems</a>. <a href="Client%E2%80%93server_model" title="Client–server model">Client–server computing</a> implemented similar principles in the 1980s with mixed success. However, in more recent years, the distributed client–server model has become considerably more difficult to maintain. As the number of transactions grew in response to various online services (especially the <a href="WWW" class="mw-redirect" title="WWW">Web</a>), a single distributed database was not a practical solution. In addition, most online systems consist of a whole suite of programs operating together, as opposed to a strict client–server model where the single server could handle the transaction processing. Today a number of transaction processing systems are available that work at the inter-program level and which scale to large systems, including <a href="Mainframe_computer" title="Mainframe computer">mainframes</a>.

</p><p>One effort is the <a href="X/Open_XA" title="X/Open XA">X/Open Distributed Transaction Processing</a> (DTP) (see also <a href="Java_Transaction_API" class="mw-redirect" title="Java Transaction API">Java Transaction API</a> (JTA). However, proprietary transaction-processing environments such as IBM's <a href="CICS" title="CICS">CICS</a> are still very popular, although CICS has evolved to include open industry standards as well.

</p><p>The term extreme transaction processing (XTP) was used to describe transaction processing systems with uncommonly challenging requirements, particularly throughput requirements (transactions per second). Such systems may be implemented via distributed or cluster style architectures. It was used at least by 2011.<sup id="cite_ref-2" class="reference"><a href="#cite_note-2"><span class="cite-bracket">[</span>2<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-3" class="reference"><a href="#cite_note-3"><span class="cite-bracket">[</span>3<span class="cite-bracket">]</span></a></sup>

</p>

<div class="mw-heading mw-heading2"><h2 id="References">References</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .reflist{margin-bottom:0.5em;list-style-type:decimal}@media screen{.mw-parser-output .reflist{font-size:90%}}.mw-parser-output .reflist .references{font-size:100%;margin-bottom:0;list-style-type:inherit}.mw-parser-output .reflist-columns-2{column-width:30em}.mw-parser-output .reflist-columns-3{column-width:25em}.mw-parser-output .reflist-columns{margin-top:0.3em}.mw-parser-output .reflist-columns ol{margin-top:0}.mw-parser-output .reflist-columns li{page-break-inside:avoid;break-inside:avoid-column}.mw-parser-output .reflist-upper-alpha{list-style-type:upper-alpha}.mw-parser-output .reflist-upper-roman{list-style-type:upper-roman}.mw-parser-output .reflist-lower-alpha{list-style-type:lower-alpha}.mw-parser-output .reflist-lower-greek{list-style-type:lower-greek}.mw-parser-output .reflist-lower-roman{list-style-type:lower-roman}

/* end https://en.wikipedia.org/ */

</style><div class="reflist">

/* start https://en.wikipedia.org/ */

.mw-parser-output cite.citation{font-style:inherit;word-wrap:break-word}.mw-parser-output .citation q{quotes:"\"""\"""'""'"}.mw-parser-output .citation:target{background-color:rgba(0,127,255,0.133)}.mw-parser-output .id-lock-free.id-lock-free a{background:url("./mw/Lock-green.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-limited.id-lock-limited a,.mw-parser-output .id-lock-registration.id-lock-registration a{background:url("./mw/Lock-gray-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-subscription.id-lock-subscription a{background:url("./mw/Lock-red-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .cs1-ws-icon a{background:url("./mw/Wikisource-logo.svg")right 0.1em center/12px no-repeat}body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-free a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-limited a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-registration a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-subscription a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .cs1-ws-icon a{background-size:contain;padding:0 1em 0 0}.mw-parser-output .cs1-code{color:inherit;background:inherit;border:none;padding:inherit}.mw-parser-output .cs1-hidden-error{display:none;color:var(--color-error,#d33)}.mw-parser-output .cs1-visible-error{color:var(--color-error,#d33)}.mw-parser-output .cs1-maint{display:none;color:#085;margin-left:0.3em}.mw-parser-output .cs1-kern-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right{padding-right:0.2em}.mw-parser-output .citation .mw-selflink{font-weight:inherit}@media screen{.mw-parser-output .cs1-format{font-size:95%}html.skin-theme-clientpref-night .mw-parser-output .cs1-maint{color:#18911f}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .cs1-maint{color:#18911f}}

/* end https://en.wikipedia.org/ */

</style><cite id="CITEREFGrayReuter" class="citation web cs1">Gray, Jim; Reuter, Andreas. <a rel="nofollow" class="external text" href="http://research.microsoft.com/~gray/WICS_99_TP/01_WhirlwindTour.ppt">"Transaction Processing – Concepts and Techniques (Powerpoint)"</a><span class="reference-accessdate">. Retrieved <span class="nowrap">Nov 12,</span> 2012</span>.</cite></span>

</li>

<li id="cite_note-2"><span class="mw-cite-backlink"><b><a href="#cite_ref-2">^</a></b></span> <span class="reference-text"><cite id="CITEREFKoen_Vanderkimpen_and_Dirk_Deridder" class="citation news cs1">Koen Vanderkimpen and Dirk Deridder. <a rel="nofollow" class="external text" href="https://www.smalsresearch.be/speaking-at-devoxx/">"Going eXtreme for Health Care"</a>. <i>Devoxx 2011 presentation</i><span class="reference-accessdate">. Retrieved <span class="nowrap">March 18,</span> 2017</span>.</cite></span>

</li>

<li id="cite_note-3"><span class="mw-cite-backlink"><b><a href="#cite_ref-3">^</a></b></span> <span class="reference-text"><cite id="CITEREFKevin_Roebuck2011" class="citation book cs1">Kevin Roebuck (2011). <i>Extreme Transaction Processing</i>. Lightning Source. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-1-74304-266-3</bdi>.</cite></span>

</li>

</ol></div></div>

<div class="mw-heading mw-heading2"><h2 id="Further_reading">Further reading</h2></div>

<ul><li>Gerhard Weikum, Gottfried Vossen, <i>Transactional information systems: theory, algorithms, and the practice of concurrency control and recovery</i>, Morgan Kaufmann, 2002, <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>1-55860-508-8</bdi></li>

<li><a href="Jim_Gray_(computer_scientist)" title="Jim Gray (computer scientist)">Jim Gray</a>, Andreas Reuter, Transaction Processing—Concepts and Techniques, 1993, Morgan Kaufmann, <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>1-55860-190-2</bdi></li>

<li>Philip A. Bernstein, Eric Newcomer, Principles of Transaction Processing, 1997, Morgan Kaufmann, <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>1-55860-415-4</bdi></li>

<li>Ahmed K. Elmagarmid (Editor), Transaction Models for Advanced Database Applications, Morgan-Kaufmann, 1992, <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>1-55860-214-3</bdi></li></ul>

<div class="mw-heading mw-heading2"><h2 id="External_links">External links</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .side-box{margin:4px 0;box-sizing:border-box;border:1px solid #aaa;font-size:88%;line-height:1.25em;background-color:var(--background-color-interactive-subtle,#f8f9fa);display:flow-root}.mw-parser-output .infobox .side-box{font-size:100%}.mw-parser-output .side-box-abovebelow,.mw-parser-output .side-box-text{padding:0.25em 0.9em}.mw-parser-output .side-box-image{padding:2px 0 2px 0.9em;text-align:center}.mw-parser-output .side-box-imageright{padding:2px 0.9em 2px 0;text-align:center}@media(min-width:500px){.mw-parser-output .side-box-flex{display:flex;align-items:center}.mw-parser-output .side-box-text{flex:1;min-width:0}}@media(min-width:720px){.mw-parser-output .side-box{width:238px}.mw-parser-output .side-box-right{clear:right;float:right;margin-left:1em}.mw-parser-output .side-box-left{margin-right:1em}}

/* end https://en.wikipedia.org/ */

</style><style data-mw-deduplicate="TemplateStyles:r1237033735">

/* start https://en.wikipedia.org/ */

@media print{body.ns-0 .mw-parser-output .sistersitebox{display:none!important}}@media screen{html.skin-theme-clientpref-night .mw-parser-output .sistersitebox img[src*="Wiktionary-logo-en-v2.svg"]{background-color:white}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .sistersitebox img[src*="Wiktionary-logo-en-v2.svg"]{background-color:white}}

/* end https://en.wikipedia.org/ */

</style><div class="side-box side-box-right sistersitebox"><style data-mw-deduplicate="TemplateStyles:r1126788409">

/* start https://en.wikipedia.org/ */

.mw-parser-output .plainlist ol,.mw-parser-output .plainlist ul{line-height:inherit;list-style:none;margin:0;padding:0}.mw-parser-output .plainlist ol li,.mw-parser-output .plainlist ul li{margin-bottom:0}

/* end https://en.wikipedia.org/ */

</style>

<div class="side-box-text plainlist">Wikimedia Commons has media related to <span style="font-weight: bold; font-style: italic;"><a href="https://commons.wikimedia.org/wiki/Category:Transaction_processing" class="extiw external" title="commons:Category:Transaction processing">Transaction processing</a></span>.</div></div>

</div>

<ul><li><a rel="nofollow" class="external text" href="http://www.subbu.org/articles/transactions/NutsAndBoltsOfTP.html">Nuts and Bolts of Transaction Processing (1999)</a> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20141018120251/http://www.subbu.org/articles/transactions/NutsAndBoltsOfTP.html">Archived</a> 2014-10-18 at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a></li>

<li><a rel="nofollow" class="external text" href="http://www.informit.com/articles/article.aspx?p=174375">Managing Transaction Processing for SQL Database Integrity</a></li>

<li><a rel="nofollow" class="external text" href="http://msdn.microsoft.com/en-us/library/ee818756(v=vs.110).aspx">Transaction Processing</a></li></ul>

/* start https://en.wikipedia.org/ */

.mw-parser-output .hlist dl,.mw-parser-output .hlist ol,.mw-parser-output .hlist ul{margin:0;padding:0}.mw-parser-output .hlist dd,.mw-parser-output .hlist dt,.mw-parser-output .hlist li{margin:0;display:inline}.mw-parser-output .hlist.inline,.mw-parser-output .hlist.inline dl,.mw-parser-output .hlist.inline ol,.mw-parser-output .hlist.inline ul,.mw-parser-output .hlist dl dl,.mw-parser-output .hlist dl ol,.mw-parser-output .hlist dl ul,.mw-parser-output .hlist ol dl,.mw-parser-output .hlist ol ol,.mw-parser-output .hlist ol ul,.mw-parser-output .hlist ul dl,.mw-parser-output .hlist ul ol,.mw-parser-output .hlist ul ul{display:inline}.mw-parser-output .hlist .mw-empty-li{display:none}.mw-parser-output .hlist dt::after{content:": "}.mw-parser-output .hlist dd::after,.mw-parser-output .hlist li::after{content:" · ";font-weight:bold}.mw-parser-output .hlist dd:last-child::after,.mw-parser-output .hlist dt:last-child::after,.mw-parser-output .hlist li:last-child::after{content:none}.mw-parser-output .hlist dd dd:first-child::before,.mw-parser-output .hlist dd dt:first-child::before,.mw-parser-output .hlist dd li:first-child::before,.mw-parser-output .hlist dt dd:first-child::before,.mw-parser-output .hlist dt dt:first-child::before,.mw-parser-output .hlist dt li:first-child::before,.mw-parser-output .hlist li dd:first-child::before,.mw-parser-output .hlist li dt:first-child::before,.mw-parser-output .hlist li li:first-child::before{content:" (";font-weight:normal}.mw-parser-output .hlist dd dd:last-child::after,.mw-parser-output .hlist dd dt:last-child::after,.mw-parser-output .hlist dd li:last-child::after,.mw-parser-output .hlist dt dd:last-child::after,.mw-parser-output .hlist dt dt:last-child::after,.mw-parser-output .hlist dt li:last-child::after,.mw-parser-output .hlist li dd:last-child::after,.mw-parser-output .hlist li dt:last-child::after,.mw-parser-output .hlist li li:last-child::after{content:")";font-weight:normal}.mw-parser-output .hlist ol{counter-reset:listitem}.mw-parser-output .hlist ol>li{counter-increment:listitem}.mw-parser-output .hlist ol>li::before{content:" "counter(listitem)"\a0 "}.mw-parser-output .hlist dd ol>li:first-child::before,.mw-parser-output .hlist dt ol>li:first-child::before,.mw-parser-output .hlist li ol>li:first-child::before{content:" ("counter(listitem)"\a0 "}

/* end https://en.wikipedia.org/ */

</style><style data-mw-deduplicate="TemplateStyles:r1236075235">

/* start https://en.wikipedia.org/ */

.mw-parser-output .navbox{box-sizing:border-box;border:1px solid #a2a9b1;width:100%;clear:both;font-size:88%;text-align:center;padding:1px;margin:1em auto 0}.mw-parser-output .navbox .navbox{margin-top:0}.mw-parser-output .navbox+.navbox,.mw-parser-output .navbox+.navbox-styles+.navbox{margin-top:-1px}.mw-parser-output .navbox-inner,.mw-parser-output .navbox-subgroup{width:100%}.mw-parser-output .navbox-group,.mw-parser-output .navbox-title,.mw-parser-output .navbox-abovebelow{padding:0.25em 1em;line-height:1.5em;text-align:center}.mw-parser-output .navbox-group{white-space:nowrap;text-align:right}.mw-parser-output .navbox,.mw-parser-output .navbox-subgroup{background-color:#fdfdfd}.mw-parser-output .navbox-list{line-height:1.5em;border-color:#fdfdfd}.mw-parser-output .navbox-list-with-group{text-align:left;border-left-width:2px;border-left-style:solid}.mw-parser-output tr+tr>.navbox-abovebelow,.mw-parser-output tr+tr>.navbox-group,.mw-parser-output tr+tr>.navbox-image,.mw-parser-output tr+tr>.navbox-list{border-top:2px solid #fdfdfd}.mw-parser-output .navbox-title{background-color:#ccf}.mw-parser-output .navbox-abovebelow,.mw-parser-output .navbox-group,.mw-parser-output .navbox-subgroup .navbox-title{background-color:#ddf}.mw-parser-output .navbox-subgroup .navbox-group,.mw-parser-output .navbox-subgroup .navbox-abovebelow{background-color:#e6e6ff}.mw-parser-output .navbox-even{background-color:#f7f7f7}.mw-parser-output .navbox-odd{background-color:transparent}.mw-parser-output .navbox .hlist td dl,.mw-parser-output .navbox .hlist td ol,.mw-parser-output .navbox .hlist td ul,.mw-parser-output .navbox td.hlist dl,.mw-parser-output .navbox td.hlist ol,.mw-parser-output .navbox td.hlist ul{padding:0.125em 0}.mw-parser-output .navbox .navbar{display:block;font-size:100%}.mw-parser-output .navbox-title .navbar{float:left;text-align:left;margin-right:0.5em}body.skin--responsive .mw-parser-output .navbox-image img{max-width:none!important}@media print{body.ns-0 .mw-parser-output .navbox{display:none!important}}

/* end https://en.wikipedia.org/ */

</style></div><div role="navigation" class="navbox" aria-labelledby="Database_management_systems327" style="padding:3px"><table class="nowraplinks hlist mw-collapsible autocollapse navbox-inner" style="border-spacing:0;background:transparent;color:inherit"><tbody><tr><th scope="col" class="navbox-title" colspan="2"><style data-mw-deduplicate="TemplateStyles:r1239400231">

/* start https://en.wikipedia.org/ */

.mw-parser-output .navbar{display:inline;font-size:88%;font-weight:normal}.mw-parser-output .navbar-collapse{float:left;text-align:left}.mw-parser-output .navbar-boxtext{word-spacing:0}.mw-parser-output .navbar ul{display:inline-block;white-space:nowrap;line-height:inherit}.mw-parser-output .navbar-brackets::before{margin-right:-0.125em;content:"[ "}.mw-parser-output .navbar-brackets::after{margin-left:-0.125em;content:" ]"}.mw-parser-output .navbar li{word-spacing:-0.125em}.mw-parser-output .navbar a>span,.mw-parser-output .navbar a>abbr{text-decoration:inherit}.mw-parser-output .navbar-mini abbr{font-variant:small-caps;border-bottom:none;text-decoration:none;cursor:inherit}.mw-parser-output .navbar-ct-full{font-size:114%;margin:0 7em}.mw-parser-output .navbar-ct-mini{font-size:114%;margin:0 4em}html.skin-theme-clientpref-night .mw-parser-output .navbar li a abbr{color:var(--color-base)!important}@media(prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .navbar li a abbr{color:var(--color-base)!important}}@media print{.mw-parser-output .navbar{display:none!important}}

/* end https://en.wikipedia.org/ */

</style><div id="Database_management_systems327" style="font-size:114%;margin:0 4em"><a href="Database" title="Database">Database management systems</a></div></th></tr><tr><th scope="row" class="navbox-group" style="width:1%">Types</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Object_database" title="Object database">Object-oriented</a>

<ul><li><a href="Comparison_of_object_database_management_systems" title="Comparison of object database management systems">comparison</a></li></ul></li>

<li><a href="Relational_database" title="Relational database">Relational</a>

<li><a href="Comparison_of_relational_database_management_systems" title="Comparison of relational database management systems">comparison</a></li></ul></li>

<li><a href="Key%E2%80%93value_database" title="Key–value database">Key–value</a></li>

<li><a href="Column-oriented_DBMS" class="mw-redirect" title="Column-oriented DBMS">Column-oriented</a>

<li><a href="Document-oriented_database" title="Document-oriented database">Document-oriented</a></li>

<li><a href="Wide-column_store" title="Wide-column store">Wide-column store</a></li>

<li><a href="Graph_database" title="Graph database">Graph</a></li>

<li><a href="NoSQL" title="NoSQL">NoSQL</a></li>

<li><a href="NewSQL" title="NewSQL">NewSQL</a></li>

<li><a href="In-memory_database" title="In-memory database">In-memory</a>

<li><a href="Multi-model_database" title="Multi-model database">Multi-model</a>

<ul><li><a href="Comparison_of_multi-model_databases" title="Comparison of multi-model databases">comparison</a></li></ul></li>

<li><a href="Cloud_database" title="Cloud database">Cloud</a></li>

<li><a href="Blockchain-based_database" title="Blockchain-based database">Blockchain-based database</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Concepts</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Database" title="Database">Database</a></li>

<li><a href="Armstrong's_axioms" title="Armstrong's axioms">Armstrong's axioms</a></li>

<li><a href="Codd's_12_rules" title="Codd's 12 rules">Codd's 12 rules</a></li>

<li><a href="CAP_theorem" title="CAP theorem">CAP theorem</a></li>

<li><a href="Candidate_key" title="Candidate key">Candidate key</a></li>

<li><a href="Foreign_key" title="Foreign key">Foreign key</a></li>

<li><a href="PACELC_design_principle" title="PACELC design principle">PACELC design principle</a></li>

<li><a href="Superkey" title="Superkey">Superkey</a></li>

<li><a href="Surrogate_key" title="Surrogate key">Surrogate key</a></li>

<li><a href="Unique_key" title="Unique key">Unique key</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Objects</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Relation_(database)" title="Relation (database)">Relation</a>

<ul><li><a href="Table_(database)" title="Table (database)">table</a></li>

<li><a href="Column_(database)" title="Column (database)">column</a></li>

<li><a href="Database_transaction" title="Database transaction">Transaction</a></li>

<li><a href="Transaction_log" title="Transaction log">Transaction log</a></li>

<li><a href="Database_trigger" title="Database trigger">Trigger</a></li>

<li><a href="Database_index" title="Database index">Index</a></li>

<li><a href="Stored_procedure" title="Stored procedure">Stored procedure</a></li>

<li><a href="Cursor_(databases)" title="Cursor (databases)">Cursor</a></li>

<li><a href="Partition_(database)" title="Partition (database)">Partition</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Components</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Concurrency_control" title="Concurrency control">Concurrency control</a></li>

<li><a href="Data_dictionary" title="Data dictionary">Data dictionary</a></li>

<li><a href="Query_language" title="Query language">Query language</a></li>

<li><a href="Query_optimization" title="Query optimization">Query optimizer</a></li>

<li><a href="Query_Rewriting" class="mw-redirect" title="Query Rewriting">Query rewriting system</a></li>

<li><a href="Query_plan" title="Query plan">Query plan</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Functions</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Database_administration" title="Database administration">Administration</a></li>

<li><a href="Query_optimization" title="Query optimization">Query optimization</a></li>

<li><a href="Replication_(computing)#DATABASE" title="Replication (computing)">Replication</a></li>

<li><a href="Shard_(database_architecture)" title="Shard (database architecture)">Sharding</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Related topics</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Database_model" title="Database model">Database models</a></li>

<li><a href="Database_normalization" title="Database normalization">Database normalization</a></li>

<li>Database storage</li>

<li><a href="Distributed_database" title="Distributed database">Distributed database</a></li>

<li><a href="Federated_database_system" title="Federated database system">Federated database system</a></li>

<li><a href="Referential_integrity" title="Referential integrity">Referential integrity</a></li>

<li><a href="Relational_algebra" title="Relational algebra">Relational algebra</a></li>

<li><a href="Relational_calculus" title="Relational calculus">Relational calculus</a></li>

<li><a href="Relational_model" title="Relational model">Relational model</a></li>

<li><a href="Object%E2%80%93relational_database" title="Object–relational database">Object–relational database</a></li>

</ul>

</div></td></tr><tr><td class="navbox-abovebelow" colspan="2"><div>

<ul><li><span class="noviewer" typeof="mw:File"><span title="Category"></span></span> Category</li>

<li><span class="noviewer" typeof="mw:File"><span title="Outline"></span></span> <a href="Outline_of_databases" title="Outline of databases">Outline</a></li></ul>

</div></td></tr></tbody></table></div>

<div class="navbox-styles"></div><div role="navigation" class="navbox authority-control" aria-labelledby="Authority_control_databases_frameless&#124;text-top&#124;10px&#124;alt=Edit_this_at_Wikidata&#124;link=https&#58;//www.wikidata.org/wiki/Q844565#identifiers&#124;class=noprint&#124;Edit_this_at_Wikidata644" style="padding:3px"><table class="nowraplinks hlist mw-collapsible autocollapse navbox-inner" style="border-spacing:0;background:transparent;color:inherit"><tbody><tr><th scope="col" class="navbox-title" colspan="2"><div id="Authority_control_databases_frameless&#124;text-top&#124;10px&#124;alt=Edit_this_at_Wikidata&#124;link=https&#58;//www.wikidata.org/wiki/Q844565#identifiers&#124;class=noprint&#124;Edit_this_at_Wikidata644" style="font-size:114%;margin:0 4em">Authority control databases </div></th></tr><tr><th scope="row" class="navbox-group" style="width:1%">National</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"><ul><li><span class="uid"><a rel="nofollow" class="external text" href="https://id.loc.gov/authorities/sh89002252">United States</a></span></li><li><span class="uid"><a rel="nofollow" class="external text" href="https://www.nli.org.il/en/authorities/987007543994005171">Israel</a></span></li></ul></div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Other</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em"><ul><li><span class="uid"><a rel="nofollow" class="external text" href="https://lux.collections.yale.edu/view/concept/bf2495e0-cbae-47fd-912d-1f79aa7b09cc">Yale LUX</a></span></li></ul></div></td></tr></tbody></table></div></div><div><div class="zim-footer">

This article is issued from <a class="external text" title="Last edited on 2024-12-05" href="https://en.wikipedia.org/wiki/?title=Transaction_processing&oldid=1261384509">Wikipedia</a>. The text is available under <a class="external text" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Creative Commons Attribution-Share Alike 4.0</a> unless otherwise noted. Additional terms may apply for the media files.

</div>

</div></div>

</div>

</main>

</div>

</body></html>